home *** CD-ROM | disk | FTP | other *** search
- Path: solon.com!not-for-mail
- From: seebs@solutions.solon.com (Peter Seebach)
- Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.edu
- Subject: Re: ANSI C and POSIX (was Re: C/C++ knocks the crap out of Ada)
- Date: 10 Apr 1996 17:56:51 -0500
- Organization: Usenet Fact Police (Undercover)
- Message-ID: <4khebk$rak@solutions.solon.com>
- References: <dewar.828846122@schonberg> <828903511snz@genesis.demon.co.uk> <4kgjrc$4d@news.nyu.edu>
- Reply-To: seebs@solon.com
- NNTP-Posting-Host: solutions.solon.com
-
- In article <4kgjrc$4d@news.nyu.edu>, halvin <halvin@acf4.nyu.edu> wrote:
- >this might be slightly off-topic, but isn't there a difference between the
- >ANSI and POSIX versions of fprintf? if i remember correctly, the ANSI version
- >returns 0 on success and EOF on failure -- but the POSIX version returns the
- >number of characters printed, or a negative number to indicate failure.
-
- ANSI fprintf returns # bytes written also.
-
- >so which behavior should one expect in an ANSI C application that happens
- >to run in a POSIX-compliant environment? a student stumbled upon this issue,
- >and i didn't really have an answer, as i had thought that POSIX was a proper
- >superset of ANSI C.
-
- Assuming that they disagreed, an ANSI C application would expect the ANSI
- behavior, and a POSIX application would expect the POSIX behavior.
- How you tell which you are? Simple! If you use extensions of POSIX,
- you're POSIX.
-
- But since they agree, it's a moot point. :)
-
- -s
- --
- Peter Seebach - seebs@solon.com - Copyright 1996 Peter Seebach.
- C/Unix wizard -- C/Unix questions? Send mail for help. No, really!
- FUCK the communications decency act. Goddamned government. [literally.]
- The *other* C FAQ - http://www.solon.com/~seebs/c/c-iaq.html
-